-
Notifications
You must be signed in to change notification settings - Fork 1
chore: fix regex validation to enforce exact match (public or private) #443
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Conversation
|
/run pipeline |
2 similar comments
|
/run pipeline |
|
/run pipeline |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I am seeing multiple references that would benefit from this change:
condition = can(regex("public|public-and-private|private", var.service_endpoints))
Probably at least two other things.
|
/run pipeline |
|
/run pipeline |
|
/run pipeline |
|
/run pipeline |
|
🎉 This PR is included in version 2.2.6 🎉 The release is available on:
Your semantic-release bot 📦🚀 |
https://github.ibm.com/GoldenEye/issues/issues/15651
Fix regex validation to enforce exact match (public or private)